home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19970929-19971216
/
000180_news@newsmaster….columbia.edu _Sun Oct 26 00:59:37 1997.msg
< prev
next >
Wrap
Internet Message Format
|
1997-12-15
|
4KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id AAA17362
for <kermit.misc@watsun.cc.columbia.edu>; Sun, 26 Oct 1997 00:59:37 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id AAA25748
for kermit.misc@watsun; Sun, 26 Oct 1997 00:59:36 -0400 (EDT)
Path: news.columbia.edu!psinntp!news.idt.net!news-peer.gsl.net!news.gsl.net!gip.net!news-peer.sprintlink.net!news-pull.sprintlink.net!news-in-east.sprintlink.net!news.sprintlink.net!Sprint!204.122.16.44!news.eskimo.com!jimo
From: jimo@eskimo.com (Jim Osborn)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: login script beeps unexpectedly
Date: 25 Oct 1997 22:56:10 GMT
Organization: Eskimo North (206) For-Ever
Lines: 75
Message-ID: <62ttea$l2o$1@eskinews.eskimo.com>
References: <62ejvl$fpk$1@eskinews.eskimo.com> <62h9lb$pbm$1@eskinews.eskimo.com> <62icqn$582$1@apakabar.cc.columbia.edu> <62m0oj$a7h$1@eskinews.eskimo.com>
NNTP-Posting-Host: eskimo.com
Xref: news.columbia.edu comp.protocols.kermit.misc:7960
In article <62m0oj$a7h$1@eskinews.eskimo.com>,
Jim Osborn <jimo@eskimo.com> wrote:
>I will clean up those unchecked failure possibilities, but I think
>the mystery beep must come from elsewhere. Unfortunately (or is
>it really fortunately?:) I don't get offered that awful modem often
>enough to test the script at will. I'll try relaxing the xif
>conditions to something more frequent and let you know how the
>cleanup influences things.
After more experimentation, I've found a workaround. I'd be curious
what this indicates the cause is, and for pointers on how to avoid
the root problem in the first place.
The workaround is to leave out the echo statement when aborting the
login process. It seems any echo statement causes a beep, even though
no beep is indicated in the echo statement. For example:
define eskimo {
while not defined \%1 {
askq \%1 {Eskimo Password: }
}
:retry
dial 258-0759
if fail goto retry
in 30 {Your Selection ==>} #Initial selector
if fail goto retry
echo {\12\13This is really wierd!} #beeps!
pause 5
output 1\13 #Select Eskimo
in 60 login: #Start login process
if fail goto retry
...
beeps when the echo text appears on the screen.
My guess is that Kermit doesn't like echoing things while dialing/
connecting, but I can't imagine why it would object. Anyway,
removing the echo statement from the abort process prevents an
unwanted beep, leaving the desired one free to announce success.
Jim
Here's the current version. If you can suggest improvements, lemme know. :)
define eskimo {
while not defined \%1 {
askq \%1 {Eskimo Password: }
}
:retry
dial 258-0759
if fail goto retry
in 30 {Your Selection ==>} #Initial selector
if fail goto retry
output 1\13 #Select Eskimo
in 60 login: #Start login process
if fail goto retry
out jimo\13 #Look for: Hello ,CLI,,27,<day-of-week>@seattle2
clear input
in 30 {Welcome to eskimo.com.} #Read Annex ID string
if fail goto retry
xif \find({CLI,,27},\v(input)) { #Start over if toxic modem
xif \find({@seattle2},\v(input)) {
# echo {\12\13Aborting 27,,2} #this causes unwanted beep
goto retry
}
}
in 30 Password:
if fail goto retry
out \%1\13
in 60 {Main Command?}
if fail goto retry
out {!}
echo \007 #^G
connect /quietly
}